Ontology-based network search engine

ABSTRACT

A method and apparatus for searching for a documents residing on a network comprises receiving a search request from a user. The search request comprises one or more search terms of an ontology. The ontology includes a plurality of terms. One or more of the plurality of terms includes a plurality of sub-category terms. One or more documents residing on the network is identified based on the one or more search terms and an ontology index. The ontology index comprises a plurality of relationships between the plurality of terms and sub-category terms of the ontology and a plurality of documents residing on the network. One or more search results that describe the one or more documents is presented to the user. The one or more documents contain the one or more search terms, or one of the plurality of sub-category terms of the one or more search terms.

BACKGROUND OF THE INVENTION

The field of the invention is related to search engines, specifically toontology-based network search engines.

DESCRIPTION OF THE RELATED ART

Search engines work by crawling the web, analyzing the web pages foundand creating an index that is used during the runtime of the searches.In most cases, an inverted index is also created that maps keywords toweb pages. Typically, keyword-based searches employ stem-basedapproaches to widen searches to relevant documents. For example, when auser enters a keyword such as “jump,” the search engine also searchesfor documents with keywords such as jumps, jumped, and jumping. A searchengine may also allow a user to do a search based on synonyms of thespecified keywords.

While this synonym searching is a powerful feature, users continue todemand improved searching capabilities.

SUMMARY OF THE INVENTION

The present invention generally provides a computer-implemented methodof registering an ontology with a search engine provider. The methodcomprises receiving an ontology definition comprising a plurality ofterms from an ontology owner. The method further comprises storing theontology definition on a search engine server, and creating an ontologyindex based on the ontology definition and a keyword index. The keywordindex includes a plurality of relationships between a plurality ofkeywords and a plurality of documents residing on a network. Theontology index includes a plurality of relationships between theplurality of terms and the plurality of documents residing on thenetwork. The method further comprises storing the ontology index.

According to one embodiment, a computer-readable storage medium containsa program which, when executed, performs an operation. The operationcomprises receiving a search request from a user, comprising one or moresearch terms. The one or more search terms are included in an ontology,and the ontology includes a plurality of terms. One or more of theplurality of terms includes a plurality of sub-category terms. Theoperation further comprises identifying one or more documents residingon the network based on the one or more search terms and an ontologyindex. The ontology index comprises a plurality of relationships betweenthe plurality of terms or sub-category terms of the ontology and aplurality of documents residing on the network. The operation furthercomprises presenting one or more search results that describe the one ormore documents to the user. The one or more documents contain the one ormore search terms, or one of the plurality of sub-category terms of theone or more search terms.

According to one embodiment, a system comprises a processor and amemory. The memory contains a program configured to register an ontologywith a search engine provider. The program, when executed on theprocessor, performs an operation. The operation comprises receiving anontology definition comprising a plurality of terms from an ontologyowner. The operation further comprises storing the ontology definitionon a search engine server and creating an ontology index based on theontology definition and a keyword index. The keyword index includes aplurality of relationships between a plurality of keywords and aplurality of documents residing on a network. The ontology indexincludes a plurality of relationships between the plurality of terms andthe plurality of documents residing on the network. The operationfurther comprises storing the ontology index.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features, advantages andobjects of the present invention are attained and can be understood indetail, a more particular description of the invention, brieflysummarized above, may be had by reference to the embodiments thereofwhich are illustrated in the appended drawings.

It is to be noted, however, that the appended drawings illustrate onlytypical embodiments of this invention and are therefore not to beconsidered limiting of its scope, for the invention may admit to otherequally effective embodiments.

FIG. 1 is a block diagram illustrating a system for ontology-basednetwork searching, according to one embodiment of the invention.

FIG. 2 is an example screen shot of a network search engine web pagethat uses ontology-based searches, according to one embodiment of theinvention.

FIG. 3 illustrates an example section of an ontology hierarchy presentedto a user in response to an ontology request, according to oneembodiment of the invention.

FIG. 4 is an example screen shot presenting search results from anontology-based search, according to one embodiment of the invention.

FIG. 5 illustrates four example documents, located on content servers,according to one embodiment of the invention.

FIG. 6A illustrates an example keyword index, according to oneembodiment of the invention.

FIG. 6B illustrates an example ontology index, according to oneembodiment of the invention.

FIG. 7 is a flowchart depicting a process for registering an ontology ona search engine server, according to one embodiment of the invention.

FIG. 8 is a flowchart describing a process for ontology-based networksearches, according to one embodiment of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Embodiments of the present invention provide ontology-based searches ona network. Generally, an ontology may be a controlled vocabulary withina specific domain of interest that describes concepts and relationsbetween concepts in a formal way. Accordingly, an ontology-based searchfor a concept term may locate both documents containing the conceptterm, and documents containing related (as defined by the ontology)concept terms, according to one embodiment. One embodiment provides aregistration process, which creates an ontology index by comparing anontology to an existing keyword index on a search engine. Thehierarchical organization of the ontology provides a way to relate termswithin both broader and narrower concepts. By using an ontology-basedsearch instead of a keyword search, a user can search for a term thatdescribes a broad concept. In response, a search engine can return tothe user a list of documents on a network that includes either theconcept term, or more narrow terms within the concept, as defined by theontology.

In the following, reference is made to embodiments of the invention.However, it should be understood that the invention is not limited tospecific described embodiments. Instead, any combination of thefollowing features and elements, whether related to differentembodiments or not, is contemplated to implement and practice theinvention. Furthermore, in various embodiments the invention providesnumerous advantages over the prior art. However, although embodiments ofthe invention may achieve advantages over other possible solutionsand/or over the prior art, whether or not a particular advantage isachieved by a given embodiment is not limiting of the invention. Thus,the following aspects, features, embodiments and advantages are merelyillustrative and are not considered elements or limitations of theappended claims except where explicitly recited in a claim(s). Likewise,reference to “the invention” shall not be construed as a generalizationof any inventive subject matter disclosed herein and shall not beconsidered to be an element or limitation of the appended claims exceptwhere explicitly recited in a claim(s).

One embodiment of the invention is implemented as a program product foruse with a computer system. The program(s) of the program productdefines functions of the embodiments (including the methods describedherein) and can be contained on a variety of computer-readable storagemedia. Illustrative computer-readable storage media include, but are notlimited to: (i) non-writable storage media (e.g., read-only memorydevices within a computer such as CD-ROM disks readable by a CD-ROMdrive) on which information is permanently stored; (ii) writable storagemedia (e.g., floppy disks within a diskette drive or hard-disk drive) onwhich alterable information is stored. Such computer-readable storagemedia, when carrying computer-readable instructions that direct thefunctions of the present invention, are embodiments of the presentinvention. Other media include communications media through whichinformation is conveyed to a computer, such as through a computer ortelephone network, including wireless communications networks. Thelatter embodiment specifically includes transmitting information to/fromthe Internet and other networks. Such communications media, whencarrying computer-readable instructions that direct the functions of thepresent invention, are embodiments of the present invention. Broadly,computer-readable storage media and communications media may be referredto herein as computer-readable media.

In general, the routines executed to implement the embodiments of theinvention, may be part of an operating system or a specific application,component, program, module, object, or sequence of instructions. Thecomputer program of the present invention typically is comprised of amultitude of instructions that will be translated by the native computerinto a machine-readable format and hence executable instructions. Also,programs are comprised of variables and data structures that eitherreside locally to the program or are found in memory or on storagedevices. In addition, various programs described hereinafter may beidentified based upon the application for which they are implemented ina specific embodiment of the invention. However, it should beappreciated that any particular program nomenclature that follows isused merely for convenience, and thus the invention should not belimited to use solely in any specific application identified and/orimplied by such nomenclature.

FIG. 1 is a block diagram illustrating a system 100 for ontology-basednetwork searching, according to one embodiment of the invention. Ingeneral, the networked system 100 includes a client (e.g., user's)computer 102, at least one content server 122 (four such servers 122 areshown), and a search engine server 142. The client 102, content server122, and search engine server 142 are connected via a network 120. Ingeneral, the network 120 may be a local area network (LAN) and/or a widearea network (WAN). In a particular embodiment, the network 120 is theInternet. Servers 122 may be distinct web servers for differentwebsites. Such websites may include e-commerce sites, news sites, or anyother website with a uniform resource locator, accessible from clientcomputer 102 over a network 120, as described herein.

The client computer 102 includes a Central Processing Unit (CPU) 104connected via a bus 117 to a memory 106, storage 118, an input device114, an output device 116, and a network interface (I/F) device 112. Theprocessor 104 could be any processor used to perform an embodiment ofthe invention. The input device 114 can be any device to give input tothe client computer 102. For example, a keyboard, keypad, light pen,touch-screen, track-ball, or speech recognition unit, audio/videoplayer, and the like could be used. The output device 116 can be anydevice to give output to the user, e.g., any conventional display screenor set of speakers, along with their respective interface cards, i.e.,video cards and sound cards (not shown). Although shown separately fromthe input device 114, the output device 116 and input device 114 couldbe combined. For example, a display screen with an integratedtouch-screen, a display with an integrated keyboard, or a speechrecognition unit combined with a text speech converter could be used.

The network interface device 112 may be any entry/exit device configuredto allow network communications between the client computer 102, thecontent servers 122, and the search engine server 142 via the network120. For example, the network interface device 112 may be a networkadapter or other network interface card (NIC).

Storage 118 is preferably a Direct Access Storage Device (DASD).Although it is shown as a single unit, it could be a combination offixed and/or removable storage devices, such as fixed disc drives,floppy disc drives, tape drives, removable memory cards or opticalstorage. The memory 106 and storage 118 could be part of one virtualaddress space spanning multiple primary and secondary storage devices.

The client computer 102 is generally under the control of an operatingsystem 108, which is shown in the memory 106. Illustrative operatingsystems, which may be used to advantage, include Linux and MicrosoftWindows. More generally, any operating system supporting the browser 110functions disclosed herein may be used.

The memory 106 is preferably a random access memory sufficiently largeto hold the necessary programming and data structures of the invention.While the memory 106 is shown as a single entity, it should beunderstood that the memory 106 may in fact comprise a plurality ofmodules, and that the memory 106 may exist at multiple levels, from highspeed registers and caches to lower speed but larger DRAM chips.

Illustratively, the memory 106 includes an application 110 that, whenexecuted on CPU 104, provides support for locating network addresses atone or more of the servers 122 and 142, and exchanging informationbetween the client 102 and the various servers 122 and 142. In oneembodiment, the application 110 is a browser that includes a web-basedGraphical User Interface (GUI), which allows the user to navigate anddisplay web-pages located on the Internet. However, more generally theapplication may be a thin client application configured to transfer data(e.g., HTML, XML, etc.) between the client computer 102, the servers122, and the search engine server 142 via, for example, HTTP. By way ofexample only, the application 110 will be referred to herein as abrowser.

Content server 122 generally comprises a CPU 124, a memory 126, astorage device 134, and a network interface device 132, coupled to oneanother by a bus 137. The memory 126 may be a random access memorysufficiently large to hold the necessary programming and data structuresthat are located on the content server 122. The programming and datastructures may be accessed and executed by the CPU 124 as needed duringoperation. As shown, the memory 126 includes a presentation server 128and a content application 130.

The presentation server 128 is adapted to service requests from theclient computer 102, which invoke the content application 130. In turn,the content application 130 may perform various functions which includegenerating, accessing and/or populating electronic documents 136 (e.g.,markup language documents such as HTML documents and XML documents)residing on the content server 122

As used herein, an electronic document 136 is machine-readable data,regardless of the medium of storage or transmission. In one embodiment,the documents 136 are web-pages each having an associated networkaddress. Although the documents are shown in FIG. 1 residing on thecontent server 122, it should be understood that the documents 136 neednot be static, but instead may be generated by the content application130.

The document 136 may then be served to a requesting browser 110 on arespective client computer 102. The browser 110 may display the document136 to a user operating the client computer 102.

By way of illustration, the presentation server 128 may be an instanceof Apache, Tomcat or IBM Web Sphere products. Web Sphere is availablefrom International Business Machines, Inc. Further, the contentapplication 130 may be configured to access a back end database (notshown), or perform other functions. By way of illustration, the contentapplication 130 may be a stock quote retrieval application, ane-commerce application such as eBay, or an e-business application suchas IBM Connect, or a Portal environment such as IBM Web Sphere portalserver, which runs in an application environment. However, moregenerally, it is contemplated that the invention is adaptable to anyapplication server and applications.

Search engine server 142 generally comprises a CPU 144, a memory 146, astorage device 154, and a network interface device 152, coupled to oneanother by a bus 157. The memory 146 may be a random access memorysufficiently large to hold the necessary programming and data structuresthat are located on the search engine server 142. The programming anddata structures may be accessed and executed by the CPU 144 as neededduring operation.

As shown, the memory 146 includes a presentation server 148, a searchengine application 150, and an ontology manger 158. The presentationserver 148 is adapted to service requests from the client computer 102which invoke the search engine 150. In turn, the search engine 150 mayperform various functions which include generating, and/or populatingelectronic documents 164 (e.g., markup language documents such as HTMLdocuments and XML documents) residing on the search engine server 142.Although the documents 164 are shown in FIG. 1 residing on the server142, it should be understood that the documents 164 need not be static,but instead may be generated by the search engine 150. Embodiments of asearch engine 150, and ontology manager 158, are described in furtherdetail in the following discussion.

Storage 154 is preferably a Direct Access Storage Device (DASD).Although it is shown as a single unit, it could be a combination offixed and/or removable storage devices, such as fixed disc drives,floppy disc drives, tape drives, removable memory cards or opticalstorage. The memory 146 and storage 154 could be part of one virtualaddress space spanning multiple primary and secondary storage devices.

As shown, the storage 154 includes a keyword index 156, ontology indices160 and ontology hierarchies 162. The keyword index 156 is typically adata structure created by search engine 150. Periodically, the searchengine 150 ‘crawls’ the network to access all the content servers 122,and analyzes the text within all the electronic documents 136 on thosecontent servers 122. The search engine 150 may create a keyword index156 that associates text, or keywords, within the documents 136 to thenumerous documents 136 that contain the keyword. The keyword index 156enables a search engine 150 to quickly respond to a user's request fordocuments 136 related to user-specified keyword(s).

In response to a user requesting a search based on a keyword, a searchengine 150 typically returns a list within an electronic document 164,wherein each entry describes the electronic documents 136 associatedwith that keyword in the keyword index 156. Queries may use Booleanlogic to combine keyword searches. The result of an “AND” operation isan intersection of the individual keyword components results. The resultof an “OR” operation is a union of the individual keyword componentresults.

The ontology manager 158 may derive ontology indices 160 by comparingontology hierarchies 162 to the keyword index 156. Ontology hierarchies162 generally consist of a number of specific terms. Each term may alsodescribe a category that contains other terms (also referred to hereinas sub-categories). Accordingly, the phrases term and category are usedinterchangeably herein. A representative portion of an ontologyhierarchy for “neurology” may appear as follows:

I. Mental Disorder

a. Adjustment disorder

b. Anxiety disorder

-   -   i. Acute stress disorder    -   ii. Anxiety disorder of childhood or adolescence

When a user requests a search based on a term included in an ontologyhierarchy 162, the search engine 150 returns a list, wherein each entrydescribes the electronic documents 136 associated with the term, and allterms within the category described by the term. In the above example,an ontology search on, “Anxiety disorder,” returns a list describing alldocuments 136 associated with, “Anxiety disorder,” “Acute stressdisorder,” or “Anxiety disorder of childhood or adolescence.”Advantageously, in one embodiment, the creation of an ontology index 160does not require additional network searches for documents 136 relevantto the ontology, but instead relies on the existing keyword index 156.Further, performing a keyword search using all the terms in a broadcategory of the ontology is resource intensive. A keyword search in sucha case means a longer wait for the user to see results, and adetrimental impact on search engine 150 performance. As with keywordsearches, ontology-based term searches can be combined with Booleanlogic to get the union or intersection of results.

In some embodiments, the ontology manager 158 may restrict access toontology indices 160 and hierarchies 162. To allow owners of ontologiesthe ability to recover costs associated with building and maintainingontologies, an ontology manager 158 may implement security measures tolimit access to users paying for access to the ontology. In such a case,some ontology owners may choose to ‘publish’ their ontologies, allowingunrestricted access to the ontology for the purposes of ontology-basedsearches.

An ontology owner may be a person, group, or organization that createsand maintains an ontology hierarchy 162. In some embodiments, ontologyowners may use the ontology manager 158 to register an ontology on asearch engine server 142. Registering the ontology on the search engineserver 142 may include placing an ontology hierarchy 162 in storage 154,and creating a respective ontology index 160.

To register an ontology, an ontology owner may provide a search engineprovider with an ontology for which to create an index 160. Creating theindex 160 could be a service that the search engine provider offers toontology owners, or just an internal setup that provider performs forcommon industry ontologies. In some embodiments, the ontology owner maydefine an ontology hierarchy 162 in a standardized format, such as anOntology Markup Language (OML), or Ontology Web Language (OWL). Aregistration process may also include the selection of security options,customized to an ontology owner's preferences.

FIG. 1 is merely one hardware/software configuration for the networkedclient computer 102, content servers 122, and search engine servers 142.Embodiments of the present invention can apply to any comparablehardware configuration, regardless of whether the computer systems arecomplicated, multi-user computing apparatus, single-user workstations ornetwork appliances that do not have non-volatile storage of their own.Further, it is understood that while reference is made to particularlanguages, including HTML, XML and JAVA, the invention is not limited toa particular language, standard or version. Accordingly, persons skilledin the art will recognize that the invention is adaptable to otherlanguages and that the invention is also adaptable to future changes ina particular language as well as to other languages presently unknown.Further, the presentation server 128 and content application 130 aremerely illustrative and other embodiments adapted to support any knownand unknown protocols/functions are contemplated.

FIG. 2 is an example screen shot 200 of a network search engine Web pagethat uses ontology-based searches, according to one embodiment of theinvention. Screen 200 includes title 202, keyword entry field 204,concept handle entry field 206 and search button 208.

In embodiments of the invention, the search engine 150 looks up thekeywords 204 in an index, and returns a list of documents for thekeywords found in the index. For strict keyword searches, the index is akeyword index 156. For ontology-based searches, the index is anontology-index 160.

In this example, a user on a client computer 102 enters the keywords“anxiety disorder” into the keyword entry field 204. For anontology-based search, the user enters a concept handle in the concepthandle entry field 206. A concept handle identifies a specific ontologyindex 160 and hierarchy 162. In one embodiment of the invention,ontology owners may limit access to an ontology, by restricting theavailability of a concept handle to a specific group, such as employees,registered members of an industry group, etc. Ontology owners that wishto publish their ontologies may make their respective concept handlespublic on Web pages, industry journals, and the like.

In some embodiments, the search engine web page 200 may include adrop-down list of all public ontologies. Advantageously, providing adrop-down list of public ontologies enables a user to performontology-based searches without having to find the concept handle for aparticular ontology. Additionally, a user that is not looking for aparticular ontology may discover ontologies of interest by perusing adrop-down list of public ontologies.

In this example, a user enters a concept handle “NEUROLOGY-ONT1,” in theconcept handle entry field 206. To proceed with the ontology search, theuser may press the search button 208. Because this is an ontology-basedsearch, the ontology manager 158 presents the user with the appropriatesection of the “NEUROLOGY-ONT1 hierarchy 162” for the keywords, “ANXIETYDISORDER,” shown in FIG. 3.

According to one embodiment, a user may enter a concept handle without akeyword entry. In such a case, the search engine 150 may return adefault section of the respective ontology hierarchy 162, defined by theontology owner.

FIG. 3 illustrates an example section 300 of an ontology hierarchy 162presented to a user in response to an ontology request, according to oneembodiment of the invention.

The section 300 of hierarchy 162 “NEUROLOGY-ONT1,” includes the category308, specified in the keyword entry, “ANXIETY DISORDER,” along with theterms 310 within category 308.

Because category 308 is a sub-category of category 304, “MentalDisorder,” section 300 also includes category 304, the othersub-category 306 of category 304, and the ‘neighboring’ categories 302of the category 304.

Additionally, section 300 displays categories in an expandable format.In other words, the “+” symbols to the left of the category labelsindicate that further terms exist within a category, and are shown inresponse to a user clicking the “+” symbol. Similarly, the “−” symbolshown in section 300 indicates that an expanded category can becontracted, so as to hide the terms contained within.

In some embodiments, a user may select one or morecategories/sub-categories shown from section 300. According to oneembodiment, the user may scroll through neighboring sections of section300 for selecting other categories/sub-categories.

By viewing an ontology in a hierarchical structure, a user may findcategories related to the user's initial keyword entry. By viewingcategories related to the initial keyword entry, a user may focus anontology-based search on a specific sub-category, a related category ora wider array of categories. For example, after viewing section 300, auser could focus a search on one sub-category 310, such as “AnxietyHyperventilation.” A user could also search within a related category,such as “Adjustment Disorder,” or broaden the search to, “MentalDisorder,” or even search on “Maltreatment syndromes” instead.

When the user has finished selecting search term(s), the user may pressthe “GO” button 312. In response, the search engine 150 presents searchresults describing all documents 136 identified in the ontology index160 that contain the selected term(s), or terms within thesub-categories of the selected term(s). In this example, the userselects category 308, “Anxiety disorder,” and presses the “GO” button312. In response, the search engine presents the list 400 described inFIG. 4.

FIG. 4 is an example screen shot 400 presenting search results from anontology-based search, according to one embodiment of the invention.Screen shot 400 includes title 402, and results 404. The title 402includes a “CONCEPT,” which describes the ontology searched, and a“TOPIC,” which describes the term(s) that the user selects from theontology hierarchy 162. In this example, the concept is“NEUROLOGY-ONT1,” and the topic is “Anxiety disorder.”

According to one embodiment of the invention, the results 404 includedocument titles and network addresses. FIG. 4 shows http addresses inthis example search for Internet documents. However, any network may besearched. Accordingly, the addresses displayed alongside document titlesmay indicate other types of network addresses. The results indicatedocuments 136 identified in an ontology index 162, that are associatedwith the topic, anxiety disorder, and all the sub-categories of anxietydisorder described in FIG. 3.

FIG. 5 illustrates four example documents 536, located on contentservers 122, according to one embodiment of the invention. Documents 536include, “DOCUMENTS 4-7.” Each of the documents 536 shows a smallsampling of keywords found in the document, with a notation indicatingwhere the word is positioned in the document. For example, “DOCUMENT 4,”contains keywords, “MENTAL,” at position 17, and “DISORDER,” at position18. The other documents include similar contents. For purposes of thisdiscussion, the position indicates the word position, or sequence, inthe document 536.

FIG. 6A illustrates an example keyword index 656, according to oneembodiment of the invention. As described in FIG. 1, the search engine150 creates a keyword index 156 based on the documents 136 found duringa “crawl” of content servers 122 on a network 120. In this example,keyword index 656 is derived from the documents 536, described in FIG.5.

Keyword index 656 includes a keyword column 602 and a references column604. Entries in the keyword column 602 indicate keywords found in thedocuments 536. Entries in the references column 604 indicate thespecific documents 536 that contain the keyword, the number of times thekeyword appears in the document 536, and the keyword position of eachappearance. In this example, the format of the reference is: [number ofappearances]: [document id]; [first appearance position . . . nthappearance position].

The first keyword in index 656, “anxiety,” has two references. The firstreference, “2: 5; 10, 23” indicates that the keyword, “anxiety” appears2 times in “DOCUMENT 5”, at positions 10 and 23. The second reference,“1:6; 51,” indicates that the keyword, “anxiety,” appears once in“DOCUMENT 6,” at position 51.

Keyword index 656 contains other similar entries. The document andposition numbers presented herein are merely short-hands used for thesake of clarity. In some embodiments of the invention, a document numbermay reference another index, wherein the document number is associatedwith a network address for the document. According to the details of aparticular implementation, position number may indicate line number,page number, etc.

FIG. 6B illustrates an example ontology index 660, according to oneembodiment of the invention. In this example, ontology index 660 isderived from keyword index 656, and ontology, “NEUROLOGY-ONT1,”described in FIG. 3.

According to one embodiment, the ontology index 660 includes a termscolumn 662 and a references column 664. Entries in the terms column 662indicate terms from ontology hierarchy 162 found in the documents 536,as indicated by the keyword index 656. Entries in the references column664 identify the specific documents 536 that contain a term, the numberof times the term appears in the document 536, and the position of eachappearance. In this example, the format of the reference is: [number ofappearances]: [document id]; [first appearance position . . . nthappearance position].

The second term, “Anxiety disorder,” in index 656 has two references.The first reference, “2: 5; 10, 23” indicates that the term, “anxietydisorder” appears 2 times in “DOCUMENT 5, ”, at position 10 and 23.Referring back to FIG. 5, “DOCUMENT 5” includes the term, “Anxietydisorder,” (anxiety at position 10, disorder at position 11), and theterm, “Anxiety hyperventilation.” Referring back to FIG. 3, section 300of the ontology hierarchy, “NEUROLOGY-ONT1,” includes “Anxietyhyperventilation” as a sub-category of “Anxiety disorder.” Accordingly,the appearance of both terms is recorded in the ontology index 660 forthe term, “Anxiety disorder.”

The second reference for the “Anxiety disorder” term, “2: 5; 10, 23”indicates that the term, “Anxiety disorder” appears once in “DOCUMENT6”, at position 51. Referring back to FIG. 5, “DOCUMENT 6” includes theterm, “anxiety hyperventilation,” (anxiety at position 51, andhyperventilation at position 52). As discussed previously, “Anxietyhyperventilation” as a sub-category of “Anxiety disorder.” Accordingly,the appearance of “Anxiety hyperventilation” is recorded in the ontologyindex 660 as an appearance of the term, “Anxiety disorder.” The ontologyindex 660 contains other similar entries.

FIG. 7 is a flowchart depicting a process 700 for registering anontology on a search engine server 142, according to one embodiment ofthe invention. As shown, process 700 begins at step 702, wherein anontology owner sends an ontology to a search engine server 142. Theontology may be in the form of a data file, describing the ontology in atree hierarchy structure, using a standardized format, such as anOntology Markup Language (OML), or an Ontology Web Language.

At step 704, the search engine server 142 receives the ontology, andstores an ontology tree hierarchy 162. The search engine provider mayprocess the incoming ontology using the search engine 150, or anothertool. In some embodiments, the ontology manager 158 processes theincoming ontology to create the tree hierarchy 162.

As is shown, step 706 begins a loop describing the creation of anontology index 160 that includes steps 708-714. According to oneembodiment, the search engine provider may employ a process to creatingthe ontology index 160 for ontology owners. In such a case, the searchengine 150, or another tool defined by the provider, may perform thefollowing functions. For each term contained within an ontology, at step708, the search engine 150 may create an ontology index 160 entry. Theontology index entry may be in the form of the ontology index entriesdescribed in FIG. 6B. At step 710, the search engine 150 may search thekeyword index 156 for the term. Searching for a term containing morethan one word requires combining references within the keyword index 156to ensure that all the words of the term appear in one document,consecutively, and in the proper sequence.

As is shown, at step 712, another loop begins including step 714. Foreach reference found for the term, the search engine 1 50 stores thereference in the ontology index 156 for the term entry. Additionally,the search engine 150 stores the same reference for all theterms/categories in the ontology index 160 that contain the referencedterm.

At the conclusion of loop 712, the process 700 continues for the nextterm in the ontology tree hierarchy 162. At the conclusion of loop 706,the process continues to step 716.

At step 716, the search engine 150 may store the ontology index 160. Atstep 718, the search engine 150 creates an ontology handle identifyingthe ontology index, and sends the ontology handle to the ontology owner,completing process 700.

In some embodiments, the ontology manager 158 may create the ontologyindex 160. In such a case, the ontology manager 158, instead of thesearch engine 150, may perform the steps 706-716, described above.

FIG. 8 is a flowchart describing a process 800 for ontology-basednetwork searches, according to one embodiment of the invention. Asshown, process 800 begins at step 802, wherein an ontology ownerpublishes an ontology handle, either to a restricted group, or publicly.

At step 804, a user invokes a search engine 150 that performsontology-based searches. A further requirement of the search engine 150is that the search engine 150 resides on a server 142 that the desiredontology is registered on.

At step 806, the user uses the ontology handle to request a view of theontology hierarchy 162. In some embodiments, the user may enter one ormore keywords such that a specific section of the hierarchy 162,indicated by the keyword(s), is presented to the user.

At step 808, the user sends a request for an ontology-based search tothe search engine 150, including one or more terms selected from thehierarchy 162. At step 810, the search engine 150 searches therespective ontology index 160 for the specified ontology hierarchy 162for references to the user-selected terms.

At step 812, the search engine 150 presents a list to the user,indicating all documents 136 referenced in the ontology index 160 thatcontain the user-selected term(s). Additionally, for terms that containterms, or sub-categories, the search engine 150 also includes documents136 in the list that reference the sub-categories.

In some embodiments, the list may contain a title for each document inthe list, and a network address. The particular details of a list entrymay vary according to the particular embodiment.

While the foregoing is directed to embodiments of the present invention,other and further embodiments of the invention may be devised withoutdeparting from the basic scope thereof, and the scope thereof isdetermined by the claims that follow.

1. A computer-implemented method of registering an ontology with asearch engine provider, comprising: receiving an ontology definitioncomprising a plurality of terms from an ontology owner; storing theontology definition on a search engine server; creating an ontologyindex based on the ontology definition and a keyword index, wherein: thekeyword index includes a plurality of relationships between a pluralityof keywords and a plurality of documents residing on a network; theontology index includes a plurality of relationships between theplurality of terms and the plurality of documents residing on thenetwork; and storing the ontology index.
 2. The method of claim 1,further comprising: providing an interface to the search engine server,wherein a user may specify search terms for searching the ontologyindex.
 3. The method of claim 2, further comprising: receiving a searchrequest, comprising one or more search terms of the ontology;identifying one or more documents residing on the network based on theone or more search terms, the ontology, and the ontology index; andpresenting one or more search results that describe the one or moredocuments to the user, wherein the one or more documents contain the oneor more search terms, or a sub-category term of the one or more searchterms.
 4. The method of claim 1, further comprising: generating anontology handle, wherein an ontology handle enables a user to view theontology definition and search the ontology index; sending the ontologyhandle to the ontology owner.
 5. The method of claim 1, wherein theontology definition comprises either: Ontology Markup Languagestatements; or Ontology Web Language statements.
 6. The method of claim1, further comprising: providing an interface to the search engineserver, wherein a user may specify search terms for searching theontology.
 7. The method of claim 6, wherein the interface furthercomprises a drop-down selectable list of a plurality of publiclyavailable ontologies.
 8. A computer-readable storage medium containing aprogram which, when executed, performs an operation, comprising:receiving an ontology definition comprising a plurality of terms from anontology owner; storing the ontology definition on a search engineserver; creating an ontology index based on the ontology definition anda keyword index, wherein: the keyword index includes a plurality ofrelationships between a plurality of keywords and a plurality ofdocuments residing on a network; the ontology index includes a pluralityof relationships between the plurality of terms and the plurality ofdocuments residing on the network; and storing the ontology index. 9.The computer-readable storage medium of claim 8, further comprising:providing an interface to the search engine server, wherein a user mayspecify search terms for searching the ontology index.
 10. Thecomputer-readable storage medium of claim 9, further comprising:receiving a search request, comprising one or more search terms of theontology; identifying one or more documents residing on the networkbased on the one or more search terms, the ontology, and the ontologyindex; and presenting one or more search results that describe the oneor more documents to the user, wherein the one or more documents containthe one or more search terms, or a sub-category term of the one or moresearch terms.
 11. The computer-readable storage medium of claim 8,further comprising: generating an ontology handle, wherein an ontologyhandle enables a user to view the ontology definition and search theontology index; sending the ontology handle to the ontology owner. 12.The computer-readable storage medium of claim 8, wherein the ontologydefinition comprises either: Ontology Markup Language statements; orOntology Web Language statements.
 13. The computer-readable storagemedium of claim 8, further comprising: providing an interface to thesearch engine server, wherein a user may specify search terms forsearching the ontology.
 14. The computer-readable storage medium ofclaim 13, wherein the interface further comprises a drop-down selectablelist of a plurality of publicly available ontologies.
 15. A system,comprising: a processor; a memory containing a program configured toregister an ontology with a search engine provider, the program, whenexecuted on the processor, performs an operation, comprising: receivingan ontology definition comprising a plurality of terms from an ontologyowner; storing the ontology definition on a search engine server;creating an ontology index based on the ontology definition and akeyword index, wherein: the keyword index includes a plurality ofrelationships between a plurality of keywords and a plurality ofdocuments residing on a network; the ontology index includes a pluralityof relationships between the plurality of terms and the plurality ofdocuments residing on the network; and storing the ontology index. 16.The system of claim 15, further comprising: providing an interface tothe search engine server, wherein a user may specify search terms forsearching the ontology index.
 17. The system of claim 15, furthercomprising: generating an ontology handle, wherein an ontology handleenables a user to view the ontology definition and search the ontologyindex; sending the ontology handle to the ontology owner.
 18. The systemof claim 15, wherein the ontology definition comprises either: OntologyMarkup Language statements; or Ontology Web Language statements.
 19. Thesystem of claim 15, further comprising: providing an interface to thesearch engine server, wherein a user may specify search terms forsearching the ontology.
 20. The system of claim 19, wherein theinterface further comprises a drop-down selectable list of a pluralityof publicly available ontologies.